Optional analytics rule filter for object properties. - #821
Merged
Merged
Conversation
bsriramprasad
requested changes
Aug 13, 2026
melanconj
approved these changes
Aug 17, 2026
venki5685
approved these changes
Aug 20, 2026
mfournier-genetec
approved these changes
Aug 20, 2026
Contributor
|
suggestion to keep ObjectProperties as a Generic Parameter for The Rule Description instead of limiting ObjectDetection rule itself. So that device vendors can easily adapt for any Analytic Rule as needed. |
venki5685
approved these changes
Aug 26, 2026
bsriramprasad
approved these changes
Sep 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The proposal allows expressing filtering for arbitrary object properties.
By purpose no requirements on supported filtering is included as implementations typically do not implement filtering on the XML DOM tree.